Skip to content

fix: correct typos in source and docs - #570

Open
TheGreatApollyon wants to merge 1 commit into
emmett-framework:masterfrom
TheGreatApollyon:fix/typos
Open

fix: correct typos in source and docs#570
TheGreatApollyon wants to merge 1 commit into
emmett-framework:masterfrom
TheGreatApollyon:fix/typos

Conversation

@TheGreatApollyon

Copy link
Copy Markdown

Fixes several typos across the codebase:

  • SuccesfullySuccessfully (commands.py, migrations.md)
  • instaceinstance (testing.md)
  • reccomendrecommend (migrations.md)

- Succesfully → Successfully (commands.py, migrations.md)
- instace → instance (testing.md)
- reccomend → recommend (migrations.md)
Copilot AI review requested due to automatic review settings July 31, 2026 06:07

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR cleans up several typos in Emmett’s migration CLI output strings and the related documentation, improving professionalism and keeping the docs aligned with actual command output.

Changes:

  • Corrected “Succesfully” → “Successfully” in migration command output strings and in migration docs examples.
  • Corrected “instace” → “instance” in the testing documentation.
  • Corrected “reccomend” → “recommend” in the migrations documentation.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File Description
emmett/orm/migrations/commands.py Fixes user-facing CLI output typos for up/down/set migration commands.
docs/testing.md Fixes a typo in the database fixture explanation text.
docs/orm/migrations.md Fixes typos in migration docs narrative and command output examples.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread docs/orm/migrations.md
In the next sections we will describe all of this using the *bloggy* application we saw in the [tutorial chapter](../tutorial) as an example.

> **Note:** we **strongly reccomend** you to not enable automatic migrations on applications that run on production environments. The automatic migrations and the ones performed by the migration engine have some slight differences; while we will document operations supported by the second system, the detection performed by the automatic one depends on the [pydal](https://github.com/web2py/pydal) library, and are not officially supported by the Emmett development. If you need more informations about this you should check the [web2py docs](http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Migrations).
> **Note:** we **strongly recommend** you to not enable automatic migrations on applications that run on production environments. The automatic migrations and the ones performed by the migration engine have some slight differences; while we will document operations supported by the second system, the detection performed by the automatic one depends on the [pydal](https://github.com/web2py/pydal) library, and are not officially supported by the Emmett development. If you need more informations about this you should check the [web2py docs](http://www.web2py.com/books/default/chapter/29/06/the-database-abstraction-layer#Migrations).
Comment thread docs/testing.md
```

As you can see, we called the `generate_runtime_migration` method with our application database instance, applied the generated migration before yielding the database instace, and reverted the migration immediately after. Every test function we'll write using this fixture, will have a migrated database to test.
As you can see, we called the `generate_runtime_migration` method with our application database instance, applied the generated migration before yielding the database instance, and reverted the migration immediately after. Every test function we'll write using this fixture, will have a migrated database to test.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants